OpenEdge Development:<br />Progress 4GL Reference VALIDATE statement

Verifies that a record complies with mandatory field and unique index definitions.

Syntax

VALIDATE `record` [ NO-ERROR ]

To validate a record in a table defined for multiple databases, you must qualify the record’s table name with the database name. See the Record phrase reference entry for more information.

Specifies that any errors that occur in the attempt to validate the record are suppressed. After the VALIDATE statement completes, you can check the ERROR-STATUS system handle for information on any errors that occurred.

This procedure prompts for an item number. If an item with that number is not available, the procedure creates a new item record and lets you supply some item information. The VALIDATE statement checks the data you enter against the index and mandatory field criteria for the item record.

r-valid.p
REPEAT FOR item: PROMPT-FOR item-num. FIND item USING item-num NO-ERROR. IF NOT AVAILABLE item THEN DO: CREATE item. ASSIGN item-num. UPDATE item-name price. VALIDATE item. END. ELSE DISPLAY item-name price. END.

r-valid.p

REPEAT FOR item:
  PROMPT-FOR item-num.
  FIND item USING item-num NO-ERROR.
  IF NOT AVAILABLE item THEN DO:
    CREATE item.
    ASSIGN item-num.
    UPDATE item-name price.
    VALIDATE item.
  END.
  ELSE DISPLAY item-name price.
END.

Notes

Because validation is done automatically, you rarely have to use the VALIDATE statement. Progress automatically validates a record when a record in the record buffer is replaced by another, a record’s scope iterates or ends, the innermost iterating subtransaction block that creates a record iterates, or a transaction ends. For more information on record scoping and subtransaction blocks, see the chapter on block properties in OpenEdge Development: Progress 4GL Handbook .

Progress automatically validates mandatory fields when those fields are modified.

If the validation fails on a newly-created record, VALIDATE raises the ERROR condition.

Progress performs validation when it leaves a field.

For complex validations, it might be easier to use the IF...THEN...ELSE statement instead of the VALIDATE statement.

You cannot use the VALIDATE statement to test fields that are referenced in SQL statements, since validation is not performed for these fields.

If a field or table has been modified, the VALIDATE statement causes WRITE events and all related WRITE triggers to execute.

VALIDATE statement

Syntax

Notes

See also